RP/0/RP0/CPU0:rtr(config)#group BGPV6
RP/0/RP0/CPU0:rtr(config-GRP)# router bgp '.*'
RP/0/RP0/CPU0:rtr(config-GRP-bgp)# neighbor '::'
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr)# address-family ipv6 unicast
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)# !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)# !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)# !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)#end-group
RP/0/RP0/CPU0:rtr(config)#commit
Fri Sep 11 09:14:15.770 UTC
RP/0/RP0/CPU0:Sep 11 09:14:16.154 : config[65900]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'xxx'. Use 'show configuration commit changes 1000000314' to view the changes.
that was accepted by the cli at least :)
this really needs to be somewhere in the doc or the cli ;p
thanks Xander
Mik
... View more
Hi,
in XR 4.3.2 I used to have :
group mygroup
router bgp '.*'
neighbor '.*'
!
!
end-group
to match all neighbors (IPv4 + IPv6)
but I can't make that work with XR 5.3.1 which seems to check the regexp on "neighbor" very hard:
myrtr(config-GRP-bgp)# neighbor '.*'
^
% Invalid input detected at '^' marker.
the CLI suggests a regexp for IPv4 neighbors, which is accepted :
myrtr(config-GRP-bgp)#neighbor ?
A.B.C.D or X:X::X 'RegExp': Neighbor address with strict dot/colon match. Eg. '[0-9]*\..*\..*\..*'
router bgp '.*'
neighbor '[0-9]*\..*\..*\..*'
!
!
but it does not propose an IPv6 one and all I tried were rejected ;)
any idea to match IPv6 neighbors ?
thanks
Mik
... View more
thanks Xander,
all was fine, just did not know the OID to poll :)
so I got it this time :
SNMPv2-SMI::enterprises.9.9.91.1.1.1.1.4.2630860 = INTEGER: 425
which correctly match :
RP/0/RP0/CPU0:xxxx#show controllers te0/10/0/4 phy | i Power
Tx Power: 0.70110 mW (-1.54220 dBm)
Rx Power: 0.42580 mW (-3.70794 dBm)
thanks again
cheers
Mik
... View more
Hi, I can't seem to find an OID to monitor transceiver optics RX/TX as "dbm" on IOS-XR like we can do on catalyst/IOS devices for example ENTITY-SENSOR-MIB only seems to report celsius/amperes/watts/voltsDC sensors ? thanks Mik
... View more
for the record, any "BE" aliases only work in exec mode and there is no plan to fix that
for example, in config mode you cannot do :
conf t
int Be123
neither can you do :
do show int be123
in the end, this makes the whole alias even more disturbing than it's absence ...
... View more