Model: vchauhan0905/bge-base-network-test
Author: vchauhan0905
Pipeline: sentence-similarity
Library: sentence-transformers
Tags: sentence-transformers, safetensors, bert, sentence-similarity, feature-extraction, generated_from_trainer, dataset_size:414, loss:MatryoshkaLoss, loss:MultipleNegativesRankingLoss, arxiv:1908.10084, arxiv:2205.13147, arxiv:1705.00652, base_model:BAAI/bge-base-en-v1.5, base_model:finetune:BAAI/bge-base-en-v1.5, model-index, text-embeddings-inference, endpoints_compatible, region:us
Base models (finetune): id: BAAI/bge-base-en-v1.5
Card metadata: tags: sentence-transformers, sentence-similarity, feature-extraction, generated_from_trainer, dataset_size:414, loss:MatryoshkaLoss, loss:MultipleNegativesRankingLoss
base_model: BAAI/bge-base-en-v1.5
widget: source_sentence: Initiates a ping from the switch and displays the results visually to see latency over time.
Troubleshooting Console (read-only CLI terminal)
The troubleshooting console can be opened using the “Tools” tab of the switch details page. It is available only for Dashboard administrators with full (read/write)
access.
The console provides read-only access to "show" commands through a console emulator to assist with troubleshooting operations. Write commands and
configuration are not permitted.
10 The “Detach” button will open the console in a new tab.
Alternatively, the console can be launched using the “Launch Terminal” button on the left side of the switch details page.
MAC forwarding table
Displays the MAC addresses of clients learned via layer 2 interfaces, including the associated VLAN and physical port number.
Switch ports page
This functions similarly to MS switches. The name of each port comes from the abbreviated interface name from IOS-XE (e.g. Gi1/0/1 for GigabitEthernet1/0/1).
If a description is included in the configuration on the CLI, this will be shown as well.
Cloud-monitored switch troubleshooting console limitations:
• The console will proxy individual commands to the CLI of the switch through the cloud. It does not establish a persistent connection.
• Only full read/write Dashboard administrators have access to the troubleshooting console. Read-only Dashboard users are not permitted
access to the console.
sentences: What troubleshooting tools are available from Dashboard for Cloud monitored switches?, Why am I seeing traffic from a 6.X.X.X IP reach my syslog server?, What types of applications can Meraki Insight track?, source_sentence: SAML does support the use of multiple organizations. Similarly to traditional logins, it needs to determine that the user is identical across the affected
organizations. Thus, for this to occur, the following must be identical across the designed organizations:
• X.509 cert fingerprint for the organization (case sensitive)
• SAML administrator role (as only one role attribute can be used in the token)
◦ The permissions granted can be different in each Organization, but the role name must be identical
When this occurs, the user will be directed to the MSP portal and receive the desired permissions in each organization. The Consumer URL for any of the MSP
organizations can be used, as they will all direct the user to the MSP portal.
Troubleshooting
If errors are presented when attempting to log in with SAML SSO, log in as a traditional administrator and review the SAML login history. This is located on the
Organization > Administrators page, directly under the SAML administrator roles title. This includes a history of attempted SAML logins, any errors
encountered, and what username/role was provided in the assertion.
For additional information on resolving possible error messages, please refer to the article on SAML Login History Error Messages.
Receiving e-mails or alerts with SAML SSO
Due to the ability to provide any unique value in the SAML user field, administrators logged in via SAML SSO are not able to receive emails or alerts from
sentences: How can I check if my Meraki MR access point is running in low power mode?, What should I do if I get an error when trying to login via SAML?, What should I check first if I cannot connect to the Client VPN from all devices?, source_sentence: device at this stage will allow you to add it directly to the network.
4. Enter an order number (for example 5S######) or device serial number(s) (for example, Qxxx-xxxx-xxxx) in
the box next to the blue Claim button, one per line.
5. Select Claim.
6. Tick the checkbox next to any desired devices and they will be added to the network once created.
7. Choose Create network.
Now you've successfully created a Meraki dashboard device or hardware network. Look in the left-side panel to access the network. This is where you'll be able
to configure and manage your Cisco Meraki devices. To learn more about how to combine networks after creation, refer to the Combined Dashboard Networks
article.
Creating a Systems Manager Network
To create a Systems Manager network for endpoint management, follow this process:
5 1. Log in to https://dashboard.meraki.com (or your chosen region's dashboard url) using the account created earlier.
2. From the prompt window, choose Set up Systems Manager and select Next.
3. Give the network a name, for example, "Company Phones." If the page has a drop-down for Network type,
select EMM (Systems Manager).
4. Review the page, then select Create network at the bottom of the screen.
Once complete, you've successfully created a Meraki Systems Manager network. This is where you can configure profiles, payloads, applications, and many
sentences: How can I disable all SSID broadcasts on a Meraki AP?, How do I add an MT10 to my dashboard network?, Can a mesh backhaul link operate on both 2.4GHz and 5GHz?, source_sentence: site VPN page can be adjusted and this value applies to all Auto VPN peers we have iBGP connections to. For the eBGP hold timer this is per neighbor and can
be more aggressive since this is monitoring a local link. When adjusting either value it is important to take into account load on the MX concentrator.
Platform Sizing Considerations
For Z3/c platforms we recommend only advertising a handful of aggregates or a default route to the datacenter. For the rest of the MX Security & SD-WAN
appliances we recommend sizing the BGP topology to 1500 prefixes from the DC. This is due to the fact that smaller appliances may also be running other
features such as Advanced Security and Meraki Insight etc.
Route Table Integrity
In order to maintain integrity of the route table for all MXs in the SD-WAN fabric, Meraki has implemented protection both inbound and outbound from the vpn
concentrator. To protect the integrity of the route tables inbound, there is a configurable Receive limit. In addition to protecting the integrity inbound, there is
also an AS Path ACL that is placed outbound for all eBGP peers. This AS Path ACL ensures that the Meraki ASN is always the originating ASN. This ensures
that Merakis SD WAN fabric will never be transit between two DCs. By default this is on and can be disabled by clicking the checkbox under Allow transit.
If the MX is deployed in a warm spare (high availability) configuration, the Virtual IP (VIP) will be used instead of the WAN IP address.
sentences: What prefix size should I use for my virtual network?, Why is a site NOT being blocked when it should be?, What does a flashing white LED power light refer to on MX84?, source_sentence: MX Load Balancing and Flow Preferences
All MX security appliances feature a secondary uplink that can be used for load balancing and failover purposes. This article explains how to enable and
configure a secondary uplink, load balancing between uplinks, and flow preferences for different types of traffic.
Enabling and Configuring WAN 2
Some MX models (MX75, MX84, MX85, MX95, MX105, MX250, MX400, MX450, MX600) have a dedicated secondary uplink port (WAN 2). To use these ports,
a cable just needs to be connected and the IP can be configured on the MX's local status page or through the Meraki dashboard. On all other MX models, a LAN
port can be configured as a secondary Internet port for use as WAN 2.
To enable and configure WAN 2 on an MX without a dedicated WAN 2 port:
1. Navigate to the MX's local status page.
2. Click the Configure tab at the top.
3. Under Port 1, 2, or 4 (depending on the MX model), switch the Role to Internet:
1 4. Configure the WAN port as needed:
◦ VLAN tagging - Assigns a VLAN tag to all traffic sent out of this port. If set to Don't use VLAN tagging, traffic
will be sent untagged.
◦ Connection Type - Select PPPoE if needed. Otherwise, leave as Direct.
◦ IP assignment - If the interface will get a dynamic address from the ISP, set to DHCP. Otherwise, set
to Static and configure an Address, Netmask, Gateway, and DNS servers.
sentences: How do I unlink Umbrella from my network?, Does the MX84 support dual WAN uplinks?, How do I switch between product types to take a packet capture on?
pipeline_tag: sentence-similarity
library_name: sentence-transformers
metrics: cosine_accuracy@1, cosine_accuracy@3, cosine_accuracy@5, cosine_accuracy@10, cosine_precision@1, cosine_precision@3, cosine_precision@5, cosine_precision@10, cosine_recall@1, cosine_recall@3, cosine_recall@5, cosine_recall@10, cosine_ndcg@10, cosine_mrr@10, cosine_map@100
model-index: name: SentenceTransformer based on BAAI/bge-base-en-v1.5
results: task: type: information-retrieval
name: Information Retrieval
dataset: name: dim 768
type: dim_768
metrics: type: cosine_accuracy@1
value: 0.6382978723404256
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.8297872340425532
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.8723404255319149
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.9361702127659575
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.6382978723404256
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.27659574468085113
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.174468085106383
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.09361702127659571
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.6382978723404256
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.8297872340425532
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.8723404255319149
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.9361702127659575
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.7853819442858381
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.7367021276595744
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.7392350557244175
name: Cosine Map@100
verified: no, task: type: information-retrieval
name: Information Retrieval
dataset: name: dim 512
type: dim_512
metrics: type: cosine_accuracy@1
value: 0.5957446808510638
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.8297872340425532
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.8723404255319149
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.9361702127659575
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.5957446808510638
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.27659574468085113
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.174468085106383
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.09361702127659571
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.5957446808510638
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.8297872340425532
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.8723404255319149
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.9361702127659575
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.7695703296031962
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.7152988855116515
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.7173549189533327
name: Cosine Map@100
verified: no, task: type: information-retrieval
name: Information Retrieval
dataset: name: dim 256
type: dim_256
metrics: type: cosine_accuracy@1
value: 0.6170212765957447
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.8085106382978723
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.851063829787234
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.9148936170212766
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.6170212765957447
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.26950354609929084
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.17021276595744686
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.09148936170212764
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.6170212765957447
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.8085106382978723
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.851063829787234
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.9148936170212766
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.766396441592561
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.7190898345153663
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.7225506209721818
name: Cosine Map@100
verified: no, task: type: information-retrieval
name: Information Retrieval
dataset: name: dim 128
type: dim_128
metrics: type: cosine_accuracy@1
value: 0.574468085106383
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.723404255319149
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.7872340425531915
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.8936170212765957
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.574468085106383
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.2411347517730497
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.15744680851063833
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.08936170212765956
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.574468085106383
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.723404255319149
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.7872340425531915
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.8936170212765957
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.720650028799346
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.6669537318473489
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.6717768306372212
name: Cosine Map@100
verified: no, task: type: information-retrieval
name: Information Retrieval
dataset: name: dim 64
type: dim_64
metrics: type: cosine_accuracy@1
value: 0.5531914893617021
name: Cosine Accuracy@1
verified: no, type: cosine_accuracy@3
value: 0.6808510638297872
name: Cosine Accuracy@3
verified: no, type: cosine_accuracy@5
value: 0.7872340425531915
name: Cosine Accuracy@5
verified: no, type: cosine_accuracy@10
value: 0.8085106382978723
name: Cosine Accuracy@10
verified: no, type: cosine_precision@1
value: 0.5531914893617021
name: Cosine Precision@1
verified: no, type: cosine_precision@3
value: 0.22695035460992913
name: Cosine Precision@3
verified: no, type: cosine_precision@5
value: 0.15744680851063833
name: Cosine Precision@5
verified: no, type: cosine_precision@10
value: 0.08085106382978725
name: Cosine Precision@10
verified: no, type: cosine_recall@1
value: 0.5531914893617021
name: Cosine Recall@1
verified: no, type: cosine_recall@3
value: 0.6808510638297872
name: Cosine Recall@3
verified: no, type: cosine_recall@5
value: 0.7872340425531915
name: Cosine Recall@5
verified: no, type: cosine_recall@10
value: 0.8085106382978723
name: Cosine Recall@10
verified: no, type: cosine_ndcg@10
value: 0.6788280676544856
name: Cosine Ndcg@10
verified: no, type: cosine_mrr@10
value: 0.6370567375886524
name: Cosine Mrr@10
verified: no, type: cosine_map@100
value: 0.6466524071767278
name: Cosine Map@100
verified: no
Likes: 0 | All-time downloads: 11
Created: 2025-05-01 21:23:19